I think #264 can be resolved if this PR gets merged, and transSupportBasicHtmlNodes becomes true by default.

@yoo2001818 transSupportBasicHtmlNodes is true by default, isn't it? https://react.i18next.com/latest/i18next-instance

I think #264 can be resolved if this PR gets merged, and transSupportBasicHtmlNodes becomes true by default.

@yoo2001818 transSupportBasicHtmlNodes is true by default, isn't it? https://react.i18next.com/latest/i18next-instance

No, it is true by default in i18next itself, but i18next-parser defaults to false (https://github.com/i18next/i18next-parser/blob/master/src/lexers/jsx-lexer.js#L10).

You have to match them, either by setting i18next's value to false (which will work perfectly for now), or setting i18next-parser's value to true. (which this PR tries to resolve discrepancies)

You have to match them, either by setting i18next's value to false (which will work perfectly for now), or setting i18next-parser's value to true. (which this PR tries to resolve discrepancies)

As far as i can see, i18next-parser does not have transSupportBasicHtmlNodes setting itself. Correct me if I'm wrong, but It is derived from i18next settings, with default (fallback) to false indeed.

You have to match them, either by setting i18next's value to false (which will work perfectly for now), or setting i18next-parser's value to true. (which this PR tries to resolve discrepancies)

As far as i can see, i18next-parser does not have transSupportBasicHtmlNodes setting itself. Correct me if I'm wrong, but It is derived from i18next settings, with default (fallback) to false indeed.

i18next-parser does have transSupportBasicHtmlNodes setting, however it is undocumented for now.

You may use it like this:

// i18next-parser.config.js
export default {
  lexers: {
    jsx: [{
      lexer: 'JsxLexer',
      transSupportBasicHtmlNodes: true,
    }],
  },
};

Furthermore, i18next-parser cannot read i18next's config, as i18next-parser statically analyzes the code without executing it. It doesn't actually care about i18next's configuration or its presence - it works by just reading t function call (or <Trans>) in the code. So it's the developer's job to match these config.

However, i18next itself, does set transSupportBasicHtmlNodes to true by default. What I've linked was for i18next-parser, which sets the config to false by default.

Bumped into this today and was so grateful to find not only is it reported, but there's a PR already. Could this be looked at by a maintainer?